] ObBug: /usr/openin/bin/xterm under SunOs 4.1.x will leave the tty mode ] 666 as stated here previously. After opening a call with Sun, they will ] not fix it, because they have to rewrite most of their OS, despite the ] fact that xterm released with X11R5 doesn't have this problem. ] ] Ciao, ] ] -- ] Richard Bainter Mundanely | System Analyst - OMG/CSD ] Pug Generally | Applied Research Labs - U.Texas ] pug@arlut.utexas.edu | pug@bga.com | pug@eden.com | {any user}@pug.net ] Note: The views may not reflect my employers, or even my own for that matter. ] If you do 'chmod u+s /usr/openwin/bin/xterm' the problem will go away. But then you have other problems (e.g. race condition with log file). This is the reason i did the following: commix# ls -l /usr/openwin/bin/xterm* lrwxrwxrwx 1 root 22 Feb 11 02:20 /usr/openwin/bin/xterm -> xterm.x11r5.semisecure -rwxr-xr-x 1 root 212992 Sep 26 1991 /usr/openwin/bin/xterm.sun ---s--x--x 1 root 786432 Nov 14 1993 /usr/openwin/bin/xterm.x11r5.semisecure commix# The xterm.x11r5.semisecure contains a patch posted to some newsgroup or mailinglist reducing the chances to be successfull exploitung the race condition with logfiles. I did not want to loose the logging capability. It is so big because teh X11R5 X* libraries are statically linked. -Wolfram -- Email: Wolfram.Schmidt@iao.fhg.de Voice: +49 711 970 2431 Fax: +49 711 970 2401 Office: Fraunhofer-Institut IAO, Holzgartenstr. 17, 70174 Stuttgart, Germany